Modular arms on a rotor-based remote vehicle

ABSTRACT

A rotor-based remote flying vehicle platform includes a vehicle body. The vehicle body includes a processing unit that receives positional sensor data and provides flight controls based upon the received positional sensor data. The vehicle body also includes a first frame connection interface that is configured to interface with a plurality of different arm types. The first frame connection interface comprises a physical connection and an electronic connection. Additionally, the rotor-based remote flying vehicle platform includes a first arm, of a rotor-based remote flying vehicle platform, that is selectively connectable to the vehicle body through the first frame connection interface. The first arm comprises a first arm connection interface that is selectively connectable to the first frame connection interface. Additionally, the first arm comprises a first motor mounted to the first arm.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of and priority to U.S. ProvisionalPatent Application Ser. No. 62/193,816 filed on 17 Jul. 2015 andentitled “MODULAR ARMS ON A ROTOR-BASED REMOTE VEHICLE,” whichapplication is expressly incorporated herein by reference in itsentirety.

BACKGROUND

After being used in military application for some time, so called“drones” have experienced a significant increase in public use andinterest in recent years. The proposed uses for drones has rapidlyexpanded to include everything from package delivery to mapping andsurveillance. The wide-ranging uses for drones has also created a wideassortment of different drone configurations and models. For example,some drones are physically better suited to travelling at high speed,while other drones are physically better suited for travelling longdistances.

Conventional drones typically fall within two differentcategories—fixed-wing drones and rotor-based drones. Rotor-based dronesmay comprise any number of different rotors, but a common rotorconfiguration comprises four separate rotors. Rotor-based drones provideseveral benefits over fixed-wing drones. For example, rotor-based dronesdo not require a runway to take-off and land. Additionally, rotor-baseddrones can hover over a position, and in general are typically moremaneuverable. Also, rotor-based drones are significantly more capable offlying within buildings and other structures.

Several technical limitations have slowed the wide-spread use andadoption of rotor-based drones. These technical limitations includeinsufficient control systems for achieving and maintaining flightstability, deficient sensors for accurately obtaining positional datafor the rotor-based drones, and high-power usage that both limited theflight time of rotor-based drones and increased their weight frombatteries. The increased use of rotor-based drones has presented a needfor greater flexibility within individual rotor-based drone systems thataddress one or more of these technical limitations. As such, there areseveral problems in the art to be addressed.

The subject matter claimed herein is not limited to embodiments thatsolve any disadvantages or that operate only in environments such asthose described above. Rather, this background is only provided toillustrate one exemplary technology area where some embodimentsdescribed herein may be practiced.

BRIEF SUMMARY

Embodiments disclosed herein comprise systems, methods, and apparatusconfigured to provide a highly configurable rotor-based remote flyingvehicle platform. In particular, disclosed embodiments compriserotor-based remote flying vehicle platforms with interchangeable arms.The various interchangeable arms comprise different purposes, differentoptimizations, different sensors, different motors, and other suchdifferent configurations. As such, a user can quickly and easilyconfigure a rotor-based remote flying vehicle platform to a particularneed by simply interchanging a first set of arms for a second set ofarms.

Disclosed embodiments comprise a rotor-based remote flying vehicleplatform. The rotor-based remote flying vehicle platform includes avehicle body. The vehicle body includes a processing unit that receivespositional sensor data and provides flight controls based upon thereceived positional sensor data. The vehicle body also includes a firstframe connection interface that is configured to interface with aplurality of different arm types. The first frame connection interfacecomprises a physical connection and an electronic connection.

Additionally, disclosed embodiments include a first arm, of arotor-based remote flying vehicle platform, that is selectivelyconnectable to the vehicle body through the first frame connectioninterface. The first arm comprises a first arm connection interface thatis selectively connectable to the first frame connection interface.Additionally, the first arm comprises a first motor mounted to the firstarm.

Further disclosed embodiments include a method for customizing arotor-based remote flying vehicle platform. The method comprisesreceiving, at a processing unit associated with a vehicle body, a firstindication that a first arm has been removed from a first frameconnection interface. The first indication comprises data describing oneor more operating characteristics of a first motor mounted to the firstarm. The method also comprises receiving, at the processing unitassociated with the vehicle body, a second indication that a second armhas been connection to the first frame connection interface. The secondindication comprises data describing one or more operatingcharacteristics of a second motor mounted to the second arm.Additionally, the second motor is a different type of motor than thefirst motor and is associated with different operating characteristics.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

Additional features and advantages will be set forth in the descriptionwhich follows, and in part will be obvious from the description, or maybe learned by the practice of the teachings herein. Features andadvantages of the invention may be realized and obtained by means of theinstruments and combinations particularly pointed out in the appendedclaims. Features of the present invention will become more fullyapparent from the following description and appended claims, or may belearned by the practice of the invention as set forth hereinafter.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which the above-recited and otheradvantages and features can be obtained, a more particular descriptionof the subject matter briefly described above will be rendered byreference to specific embodiments which are illustrated in the appendeddrawings. Understanding that these drawings depict only typicalembodiments and are not therefore to be considered to be limiting inscope, embodiments will be described and explained with additionalspecificity and detail through the use of the accompanying drawings inwhich:

FIG. 1 illustrates an embodiment of a quadrotor with modular arms.

FIG. 2 illustrates a close-up view of an embodiment of an arm-to-frameconnection of the quadrotor of FIG. 1.

FIG. 3 illustrates another close-up view of an embodiment of thearm-to-frame connection of the quadrotor of FIG. 1.

FIG. 4 illustrates a close-up view of an embodiment of a frameconnection interface.

FIG. 5 illustrates a close-up view of an embodiment of an arm connectioninterface.

FIG. 6A illustrates an embodiment of a quadrotor arm.

FIG. 6B illustrates another embodiment of a quadrotor arm.

FIG. 6B illustrates another embodiment of a quadrotor arm.

FIG. 6D illustrates another embodiment of a quadrotor arm.

FIG. 6E illustrates another embodiment of a quadrotor arm.

FIG. 6F illustrates another embodiment of a quadrotor arm.

FIG. 7 illustrates a flowchart for an embodiment of a method forcustomizing a rotor-based remote flying vehicle platform.

DETAILED DESCRIPTION

The following discussion now refers to a number of methods and methodacts that may be performed. Although the method acts may be discussed ina certain order or illustrated in a flow chart as occurring in aparticular order, no particular ordering is required unless specificallystated, or required because an act is dependent on another act beingcompleted prior to the act being performed.

Disclosed embodiments extend to systems, methods, and apparatusconfigured to provide a highly configurable rotor-based remote flyingvehicle platform. In particular, disclosed embodiments compriserotor-based remote flying vehicle platforms with interchangeable arms.The various interchangeable arms comprise different purposes, differentoptimizations, different sensors, different motors, and other suchdifferent configurations. As such, a user can quickly and easilyconfigure a rotor-based remote flying vehicle platform to a particularneed by simply interchanging a first set of arms for a second set ofarms.

Accordingly, disclosed embodiments allow a rotor-based remote flyingvehicle platform to be used in a wide variety of different situationsand environments. Additionally, disclosed embodiments allow arotor-based remote flying vehicle platform to be easily upgraded andextended to include functions and features that are tailored forspecific situations. For example, embodiments of the present inventioncan comprise interchangeable arms that are uniquely configured. As such,a user can customize a rotor-based remote flying vehicle platform bysimply connecting desired arms to the rotor-based remote flying vehicleplatform.

In the following disclosure various exemplary embodiments of the presentinvention are recited. One will understand that these examples areprovides only for the sake of clarity and explanation and do not limitor otherwise confine the invention to the disclosed examples.Additionally, one or more of the following examples is provided withrespect to a “quadrotor.” One will understand that the usage of a“quadrotor” is merely for the sake of clarity and that the presentinvention applies equally to all rotor-based remote flying vehicleplatforms regardless of the number of rotors.

Turning to the figures, FIG. 1 illustrates a quadrotor 100 with modulararms 110(a-d) in accordance with embodiments of the present invention.In particular, the depicted quadrotor 100 comprises multiple arms110(a-d) attached to a vehicle body 120. Additionally, the depictedquadrotor 100 comprises a processing unit in the form of flight controlunit 130 within the vehicle body 120. The flight control unit 130comprises sensors for controlling the quadrotor (e.g., altimeter,gyroscopes, GPS, sonar, etc.), along with various control and processingmodules (e.g., CPU, radio, antenna, GPU, etc.) In at least oneadditional or alternative embodiment, the flight control unit 130 and/orassociated sensors are otherwise located or dispersed through thequadrotor 100.

As such, the processing unit receives positional sensor data andprovides flight controls based upon the received positional sensor data.For example, in at least one embodiment, the processing unit receivesdata from gyroscopes and accelerometers. Using the received sensorinformation, the processing unit controls the flight of the quadrotorusing a control system, such as a PID loop.

As stated above, one will understand that the depicted quadrotor 100 ismerely exemplary. Additional or alternate embodiments of the presentinvention may comprise rotor-based remote flight systems with less thanfour arms 110(a-d) or rotor-based remote flight systems with more thanfour arms 110(a-d). Additionally, various embodiments of the presentinvention may comprise different physical configurations, constructionmaterials, proportions, and functional components. For instance,rotor-based remote flight platforms may comprise a mixture of componentssuch as cameras, sonars, laser sights, GPS, various differentcommunication systems, and other such variations.

In at least one embodiment of the present invention, the arms 110(a-d)of the quadrotor 100 are selectively removable and reconfigurable. Forexample, FIG. 2 illustrates a close-up view of an arm-to-frameconnection of the quadrotor shown in FIG. 1. In particular, FIG. 2depicts a first arm 110 a connected to the vehicle body 120 of thequadrotor 100. Additionally, a frame connector 200 and an arm connector210 are also depicted. The respective frame connector 200 and armconnector 210 may comprise any of a number of different connector types,including, but not limited to, a screw, a bolt, a mechanical clip, amechanical button, or any other connector configured to selectivelycouple two physical structures. In particular, in at least oneembodiment, the respective frame connector 200 and arm connectors 210comprise portions of an integrated connector, such as a snap-fit, thatallows a user to selectively attached an arm 110 to a vehicle body 120without removing, or otherwise, directly manipulating a connector.Instead, a forceful pull or push may be sufficient to remove and attachan arm 110.

FIG. 3 illustrates another close-up view of an arm-to-frame connectionof the quadrotor 100 depicted in Figure. In FIG. 3, the frame connector200 has been removed to reveal a frame connector hole 300. Once theframe connector 200 has been removed, the arm 110 can be easily removedphysically from the vehicle body 120 of the quadrotor 100. As statedabove, in at least one embodiment, it may not be necessary to remove aconnector 200 from the quadrotor prior to removing an arm 110. Forexample, the quadrotor 100 may comprise a button that can be pushed todisengage an arm 110 from the vehicle body 120. Additionally, in atleast one embodiment, the arm 110 may be connected to the vehicle body120 through a pressure-fit or snap-fit connection that can be overcomewith force.

Turning now to FIG. 4, FIG. 4 illustrates a close-up view of a frameconnection interface 400. The frame connection interface 400 comprisesboth the physical connection described in FIG. 2 and FIG. 3 andelectronic connections, such as a first power connection interface 410a, a second power connection interface 410 b, and a frame dataconnection interface 420. Accordingly, in at least one additional oralternative embodiment, the frame connection interface 400 provides aninterface for connecting a variety of different arms, and accompanyingaccessories, to the vehicle body 120.

In various embodiments, the frame connection interface 400 provides anextensible platform for interchanging different arms 110 with aparticular quadrotor 100. In particular, the frame connection interface400 may be configured to provide positive and negative power 410 a, 410b to arm 110 and also to provide a communication channel 420 to the arm110. As such, a replacement arm may comprise a different motor,different physical materials, a different length, additional sensors orother accessories, or any number of other difference from the originalarm 110.

FIG. 5 illustrates a close-up view of an arm connection interface 500 inaccordance with embodiments of the present invention. Similar to theframe connection interface 400, the arm connection interface 500comprises a first power connection receiver 510 a, a second powerconnection receiver 510 b, and an arm data connection interface 520. Inat least one embodiment, the various connection interfaces 510 a, 510 b,520 are integrated into a single connection interface. Similarly, in atleast one embodiment, the connection interfaces 510 a, 510 b, 520 can befurther divided than those depicted. For example, the arm dataconnection interface 520 may be further divided into a motor-controlconnection (not shown) portion for communicating control signals to amotor or motor controller and a sensor connection (not shown) forcommunicating with a sensor disposed on the arm.

In at least one embodiment, the respective frame connection interface400 and arm connection interface 500 are selectively connectable to eachother. As used herein, two objects are selectively connectable when theyare configured to be attached and removed from each other during thenormal course of use. As such, the respective frame connection interface400 and arm connection interface 500 allow a quadrotor 100 to be quicklyand easily customized for a particular job. For example, when outfittinga quadrotor for endurance flying, it may be beneficial for the quadrotor100 to comprise long arms 110(a-d) with specially tuned motors. Incontrast, when outfitting a quadrotor 100 for short, high-speed, highagility flights, it may be beneficial for the quadrotor to compriseshort arms 110(a-d) with high output motors. Accordingly, in at leastone embodiment, the frame connection interface 400 and the armconnection interface 500 allow a quadrotor 100 to be easily and quicklycustomized by simply interchanging between various alternate arms, suchas an endurance-based arm 110 with a speed-based arm 110.

Additionally, in various embodiments, it may be desirable to addfunctionality to a quadrotor 100 by interchanging various arms 110(a-d)of the quadrotor 100. For example, a quadrotor 100 may be able to gainGPS functionality by adding an arm 110 with an integrated GPS chip. TheGPS chip within the arm 110 may be configured to communicate with theflight control unit 130 through the frame data connection interface 420and the arm data connection interface 520. In at least one embodiment,the respective data connection interfaces 420, 520 may comprise aplug-and-play functionality. For instance, the data connectioninterfaces 420, 520 may comprise a USB controller configured tofacilitate communications between modules within the arm 110 and theflight control unit 130.

As an addition example, it may be desirable to add a video camerafunction to a quadrotor 100 the otherwise lacks a camera. As such, oneor more modular arms 110(a-d) with incorporated cameras can be added tothe quadrotor 100. As mentioned above, in at least one embodiment, thecameras comprise USB compatible cameras. Upon connecting the frameconnection interface 400 to the arm connection interface 400, the flightcontrol unit 130 automatically detects and configured the respective USBcameras. Additionally, in at least one embodiment, the flight controlunit 130 provides a remote user with access to the respective cameras.For instance, the flight control unit 130 may comprise a radiotransmitter that can transmit the camera data to the remote user.

In at least one embodiment, the flight control unit 130 comprises adatabase of information relating to potential arm configurations thatcan be attached to the quadrotor 100. In particular, the databasecomprises operating configurations associated with each armconfiguration. For example, a particular arm 110 may comprise a sonarfor additional flight control input. The database comprises informationnecessary for flight control unit 130 to access the sonar data,interpret the sonar data, and utilize the sonar data within flightcalculations. For instance, in at least one embodiment, the database mayalso comprise information necessary for the flight control unit toutilize the sonar data within a Kalman filter.

Additionally, in at least one embodiment, the database may compriseinformation relating to the flight dynamics of a particular arm 110. Forexample, the database may comprise appropriate PID values for stableflight with a wide variety of different arms. As stated above, variousarms 110 may comprise different lengths, different materials, differenttypes of motors, different shapes, and a myriad of other distinctions.For example, in at least one embodiment, a first arm comprises ahigh-speed motor and the first arm is constructed from a carbon fibermaterial. In contrast, a second arm comprises a heavy-lift motor and thesecond arm is constructed of high-strength aluminum. One will understandthat each of these differences can dramatically influence flightdynamics. As such, the database can provide proper flight control valuesfor each different arm configuration.

Further, in at least one embodiment, the database can comprise propervalues for a wide array of different arm configurations 110. Forexample, a particular quadrotor 100 may comprise arms 110(a-d) ofdifferent types and configurations. In at least one embodiment, thedatabase comprises information relating to the flight dynamics of avariety of different and non-uniform arm configurations such that a usercan mix-and-match the arms 110(a-d) on a quadrotor 100 and automaticallyachieve desirable flight dynamics.

Additionally, in at least one embodiment, each arm 110(a-d) may alsocomprise a memory module that stores information specific to the arm110. For example, a particular memory module associated with an arm 110may comprise control system values that can enable a flight control unit130 to maintain flight stability when using the arm. Additionally, amemory module associated with an arm 110 may comprise informationrequired for a flight controller 130 to control and access sensors andother components integrated into a particular arm 110. As such, in atleast one embodiment, a flight controller 130 can automaticallyincorporate any number of different arm configurations based uponinformation stored within an onboard database and/or information storedwithin each arm 110(a-d).

Turning now to various exemplary embodiments of modular arms for arotor-based remote flying vehicle platform, FIGS. 6A-6F illustratevarious different embodiments and/or configurations of respectivemodular arms. In particular, FIG. 6A depicts a modular arm 600 a thatcomprises a motor 610 and associated propellers. In at least oneembodiment, modular arm 600 a is used for standard flight conditionsthat do not require abnormal speed, load-bearing capacity, endurance, orother specific requirements.

In contrast, the modular arm 600 b, depicted in FIG. 6B, comprises anincreased length compared to modular arm 600 a. One of skill in the artwill understand that increased arm length impacts the flight dynamics ofan associated quadrotor in various foreseeable ways. For example, thelonger modular arm 600 b may increase the stability of a quadrotor whilein flight. As such, a user may desire to use the longer modular arm 600b during windy conditions.

Modular arm 600 c, depicted in FIG. 6C, comprises a different motor andpropeller type than the motor and propeller configuration of FIGS. 6Aand 6B. Specifically, motor 620 is larger than motor 610. In at leastone embodiment, the larger motor 620 provides greater thrust than motor610. Accordingly, a user may utilize modular arm 600 c when performinghigh-speed flight or other similar tasks.

FIG. 6D illustrates a modular arm 600 d that comprises a differentmaterial and structural configuration than the previously disclosedmodular arms 600 a, 600 b, 600 c. For example, modular arm 600 dcomprises a cut-out portion 630 that is configured to decrease theweight of the modular arm 600 d. Additionally, the modular arm 600 d isconstructed of a light material such as carbon fiber. As such, modulararm 600 d comprises a significantly lower weight than the previouslydisclosed modular arms 600 a, 600 b, 600 c. A user may desire to usemodular 600 c when performing endurance flights that are influenced bythe weight of the quad rotor.

FIG. 6E depicts an additional embodiment of a modular arm 600 c thatcomprises a sensor 640. In the depicted embodiment, the sensor 640comprises a sonar; however, in various additional or alternativeembodiments any number of different sensors may be used, such as a GPS,an altimeter, a gyroscope, an accelerometer, a camera, a lidar, aBluetooth module, a Wi-Fi module, or any other sensor device. Similarly,a modular arm 600 c may comprise a communication unit such as an analogreceiver or transmitter, a video signal receiver or transmitter, avirtual reality video stream receiver or transmitter, or similarcommunication component.

In at least one embodiment, when attaching modular arm 600 e to aquadrotor vehicle body, electronic components within modular arm 600 ecommunicate to a processing unit within the vehicle body. In particular,the modular arms communicates data that describes the variouscharacteristics of the modular arm 600 e. For example, the modular arm600 e communicates to the processing unit the motor flightcharacteristics and characteristics relating to electronic devicesembedded within the modular arms, such as sensors 640.

FIG. 6F illustrates a cutaway modular arm 600 f that depicts internalelectronics 650, 652, 660, 662, 640 within the modular arm 600 f. Inparticular, module arm 600 f comprises a positive and negative powerchannel 650, 652 and an electronic connection 660. The electronicconnection 660 is configured to communicate to electronics within themodular arm 600 e. For example, the electronic connection 660 maycomprise a motor-control connection portion for communicating controlsignals to a motor or motor controller 664 (e.g., electronic speedcontroller) and a sensor connection portion for communicating with anidentification component 662. The identification component 662 maycomprise a micro-controller, a processor, an ASIC, an FPGA, or any otherelectronic device capable of executing instructions.

In at least one embodiment, when modular arm 600 f is connected to arotor-based remote flying vehicle body, the identification component 662communicates various identification data to the control unit 130 withinthe vehicle body 120 (shown in FIG. 1). For example, the identificationcomponent 662 communicates flight dynamics data to the control unit 130for inclusion into the control system. For instance, the flight dynamicsdata may comprise identification data necessary for calculating PIDvalues for stable flight with modular arm 600 f.

Additionally, the identification component 662 is also capable ofcommunicating identification data relating to the electronics componentswithin the modular arm 600 f, such as sensors 640. For example, theidentification component 662 may communicate specifications andcommunication parameters about the sonar (sensor 640) to the controlunit 130. In particular, the identification component 662 maycommunicate sufficient information for the control unit 130 toincorporate the sonar into the control system for the vehicle. Forinstance, the control unit 130 may incorporate identification data fromthe sonar into a Kalman filter that is used to control the rotor-basedremote flying vehicle.

Accordingly, in various different or additional embodiments, a widevariety of different modular arms with different configurations andfeatures can be easily interchanged within the same rotor-based remoteflying vehicle. Further, in at least one embodiment, the rotor-basedremote flying vehicle comprises modular arms of various different types.For example, a first modular arm may comprise an additional GPS sensor,while a second modular arm comprises a camera. Both the first and secondmodular arm will impact the quadorotor differently and require differentidentification data to be sent from a respective identifier component.

One will appreciate that embodiments disclosed herein can also bedescribed in terms of flowcharts comprising one or more acts foraccomplishing a particular result. For example, FIG. 7 and thecorresponding text describe acts in various methods and systems forcustomizing a rotor-based remote flying vehicle platform. The acts ofFIG. 7 are described below.

For example, FIG. 7 illustrates that a flowchart for an embodiment of amethod 700 for customizing a rotor-based remote flying vehicle platformcan comprise an act 710 of receiving an indication that an arm has beenremoved. Act 710 includes receiving, at a processing unit associatedwith a vehicle body, a first indication that a first arm has beenremoved from a first frame connection interface. The first indicationcomprises data describing one or more operating characteristics of afirst motor mounted to the first arm. For example, as depicted anddescribed with respect to FIG. 6F, when a modular arm is removed from avehicle body, the control unit 130 detects a break in communication withthe identification component 662.

FIG. 7 also illustrates that the method 700 comprises an act 720 ofreceiving an indication that a second arm has been attached. Act 720includes receiving, at the processing unit associated with the vehiclebody, a second indication that a second arm has been connection to thefirst frame connection interface. The second indication comprises datadescribing one or more operating characteristics of a second motormounted to the second arm, wherein the second motor is a different typeof motor than the first motor and is associated with different operatingcharacteristics. For example, as depicted and described with respect toFIG. 6F, when a modular arm is connected to a vehicle body, theidentification component 662 communicates to the control unit 130 datadescribing the motor characteristics and various other characteristicsof sensors and components within the modular arm.

Additionally, FIG. 7 illustrates that the method comprises an act 730 ofcommunicating a command to the second motor. Act 730 includescommunicating a command from the processing unit to the second motor,wherein one or more aspects of the command are determined by the data.For example, as depicted and described with respect to FIG. 6F, thecontrol unit 130 communicates flight control commands to the motorcontroller 664 based upon the vehicles control system.

Accordingly, in at least one embodiment, a quadrotor can be quickly andeasily modified to incorporate any number of different features andprovide a remote user with accessing control over those features.

The present invention may be embodied in other specific forms withoutdeparting from its spirit or characteristics. The described embodimentsare to be considered in all respects only as illustrative and notrestrictive. The scope of the invention is, therefore, indicated by theappended claims rather than by the foregoing description. All changeswhich come within the meaning and range of equivalency of the claims areto be embraced within their scope.

What is claimed is:
 1. A rotor-based remote flying vehicle platformcomprising: a vehicle body, wherein the vehicle body comprises: aprocessing unit that receives positional sensor data and provides flightcontrols based upon the received positional sensor data, and a firstframe connection interface that is configured to interface with aplurality of different arm types, wherein the first frame connectioninterface comprises a physical connection and an electronic connection;a first arm that is selectively connectable to the vehicle body throughthe first frame connection interface, wherein the first arm comprises: afirst arm connection interface that is selectively connectable to thefirst frame connection interface, and a first motor mounted to the firstarm.
 2. The rotor-based remote flying vehicle platform as recited inclaim 1, further comprising an alternate arm that is selectivelyconnectable to the vehicle body, wherein the alternate arm comprises analternate arm connection interface that is selectively connectable tothe first frame connection interface.
 3. The rotor-based remote flyingvehicle platform as recited in claim 2, wherein the alternate armcomprises a different length than the first arm.
 4. The rotor-basedremote flying vehicle platform as recited in claim 2, wherein thealternate arm comprises an alternate motor that is a different type ofmotor than the first motor.
 5. The rotor-based remote flying vehicleplatform as recited in claim 2, wherein the alternate arm comprises adifferent material than the first arm.
 6. The rotor-based remote flyingvehicle platform as recited in claim 2, wherein the alternate armcomprises a sensor module that is not present within the first arm. 7.The rotor-based remote flying vehicle platform as recited in claim 1,wherein the electronic connection comprises a power connection portionfor providing power to the first motor.
 8. The rotor-based remote flyingvehicle platform as recited in claim 1, wherein the electronicconnection comprises a motor-control connection portion forcommunicating control signals to a motor or motor controller.
 9. Therotor-based remote flying vehicle platform as recited in claim 1,wherein the electronic connection comprises a sensor connection portionfor communicating with a sensor disposed on the first arm.
 10. Therotor-based remote flying vehicle platform as recited in claim 1,further comprising a second arm with an associated second motor, a thirdarm with an associated third motor, and a fourth arm with an associatedfourth motor, wherein each of the first arm, second arm, third arm, andfourth arm are selectively replaceable with a different type of arm. 11.A rotor-based remote flying vehicle platform comprising: a first armthat is selectively connectable to a vehicle body through a first frameconnection interface, wherein the first arm comprises: a first armconnection interface that is configured to physically attach to thefirst frame connection interface and to electronically communicatethrough the first frame connection interface, a first motor mounted tothe first arm, and a first identification component that communicatesfirst identification information relating to the first motor to aprocessing unit associated with the vehicle body.
 12. The rotor-basedremote flying vehicle platform as recited in claim 11, furthercomprising: the vehicle body, wherein the vehicle body comprises: theprocessing unit that receives positional sensor data and provides flightcontrols based upon the received positional sensor data, and the firstframe connection interface that is configured to interface with aplurality of different arm types, wherein the first frame connectioninterface comprises a physical connection and an electronic connection.13. The rotor-based remote flying vehicle platform as recited in claim11, wherein the first identification information also comprisesinformation that corresponds to a length of the first arm.
 14. Therotor-based remote flying vehicle platform as recited in claim 11,wherein the first identification information also comprises informationthat describes a type of motor of the first motor.
 15. The rotor-basedremote flying vehicle platform as recited in claim 11, wherein the firstidentification information also comprises information that correspondswith a type of material of the first arm.
 16. The rotor-based remoteflying vehicle platform as recited in claim 11, wherein the first armcomprises a sensor.
 17. The rotor-based remote flying vehicle platformas recited in claim 16, wherein the first identification informationalso comprises information that relates to the sensor.
 18. Therotor-based remote flying vehicle platform as recited in claim 11,further comprising a second arm with an associated second motor, a thirdarm with an associated third motor, and a fourth arm with an associatedfourth motor, wherein each of the first arm, second arm, third arm, andfourth arm are selectively replaceable with a different type of arm. 19.The rotor-based remote flying vehicle platform as recited in claim 11,further comprising: an alternate arm that is selectively connectable tothe vehicle body through the first frame connection interface, whereinthe alternate arm comprises: an alternate arm connection interface thatis configured to physically attach to the first frame connectioninterface and to electronically communicate through the first frameconnection interface, an alternate motor mounted to the first arm,wherein the alternate motor is a different type of motor than the firstmotor, and an alternate identification component that communicatesalternate identification information relating to the second motor to theprocessing unit associated with the vehicle body.
 20. A method forcustomizing a rotor-based remote flying vehicle platform comprising:receiving, at a processing unit associated with a vehicle body, a firstindication that a first arm has been removed from a first frameconnection interface; receiving, at the processing unit associated withthe vehicle body, a second indication that a second arm has beenconnection to the first frame connection interface, wherein the secondindication comprises: data describing one or more operatingcharacteristics of a second motor mounted to the second arm, wherein thesecond motor is a different type of motor than the first motor and isassociated with different operating characteristics; and communicating acommand from the processing unit to the second motor, wherein one ormore aspects of the command are determined by the data.